Method, system and device for call processing

ABSTRACT

A method, a system and a device for call processing are disclosed in the embodiments of the present invention. The method includes: obtaining, by a call initiator, address information of all or part of call managers in a network domain that processes a call, where the all or part of the call managers include a call manager that processes the call and is adjacent to the call initiator; sending, by the call initiator, a first call creating request message to an adjacent call manager according to the address information of the all or part of the call managers; and receiving, by the call initiator, a first call creating response message from the adjacent call manager. In the case that a service at a client side is required to be sent through multiple networks at a server side, inter-domain link selection and admission control may be implemented through section call processing.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/219,199, filed on Aug. 26, 2011, which is a continuation ofInternational Application No. PCT/CN2010/070738, filed on Feb. 24, 2010.The International Application claims priority to Chinese PatentApplication No. 200910037565.6, filed on Feb. 27, 2009. Theafore-mentioned patent applications are hereby incorporated by referencein their entireties.

TECHNICAL FIELD

The present invention relates to the field of communications, and inparticular, to a method, a system and a device for call processing.

BACKGROUND

In a communication network, a user may be connected with equipment ofthe user through a connection service provided by an operator network,for example, the user may be connected with two routers through anoptical connection service provided by an optical network operator. Inthe case that a control plane is introduced to a network, the controlplane defines a general protocol, which may implement fast automaticcreation of user services. The protocol includes two parts: a call andconnection, where the call is used to implement functions such asauthentication of a user access right and a switch of link informationat a user side, and the connection is mainly used to provide the userservices, that is, perform resource distribution and reservation in theoperator network.

FIG. 1 is a schematic diagram of a call model in the prior art. As shownin FIG. 1, networks at two client side are accessed to a network at aserver side through a User Network Interface (UNI) link, and the networkat the server side sends a signal at the client side to another end. Innodes at the two ends of the UNI, a node in the network at the clientside is called “UNI-C”, and a node in the network at the server side iscalled “UNI-N”.

Before creating a connection between UNI-Cs, a call is first created toimplement route information interaction of the two ends and an admissioncontrol function of the network at the server side, and after the callis successfully created, the corresponding connection is created. A callinitiated by equipment of the network at the client side may beprocessed by access equipment of the network at the server side, or mayalso be processed by a special unit, where the unit used for processinga call is called a Call Manager.

As shown in FIG. 1, before creating a connection between a UNI-C1 and aUNI-C2, the UNI-C1 initiates a call creating procedure, that is, sends acall creating request message to a UNI-N1, where the massage carriesrelated information such as a requested bandwidth. The UNI-N1 determineswhether to allow the call to be created according to a preconfiguredpolicy, and if allowed, the UNI-N1 forwards the call creating requestmessage to the UNI-N2, and then the UNI-N2 forwards the call creatingrequest message to the UNI-C2. The UNI-C2 examines information such as alocal UNI link bandwidth, and if, the requirements are met, a callcreating response message is returned to the UNI-N2, where, the messagemay carry information of local available UNI link, for designating anavailable link during connection creating. The UNI-N2 forwards the callcreating response message to the UNI-N1, and then the UNI-N1 forwardsthe message to the UNI-C1, and finally, the call is successfullycreated. In the preceding procedure, the UNI-C1, UNI-N1, UNI-N2 andUNI-C2 all have a call processing function, that is, the function of acall manager is implemented.

After the call is successfully created, a connection creating procedureis initiated, For example, the UNI-C1 sends a connection creatingrequest message to the UNI-N1 to designate a connection created onto theUNI-C2, and designate a remote link. The UNI-N1 calculates anappropriate route and creates the connection to the UNI-C2.

In the implementation of the present invention, the inventor finds thatthe call model in the prior art at least has the following problems. Anexisting General Multi-Protocol Label Switch (GMPLS) call model merelysupports end-to-end call processing, in the case that a connectionservice passes through multiple networks at a server side (it issupposed that each network at the server side is divided into onedomain), the existing call model does not support call sectionprocessing performed by each domain, therefore, functions such asinter-domain link selection and admission control of each domain are notsupported.

SUMMARY

The technical problem that embodiments of the present invention need tosolve is: to provide a method, a system and a device for callprocessing, so as to eliminate a defect that call section processingperformed by each domain is not supported in the case that a service ata client side passes through multiple networks at a server side in theprior art.

In order to solve the preceding problem, an embodiment of the presentinvention provides a call processing method, where the method includes:

obtaining, by a call initiator, address information of all or part ofcall managers in a network domain that processes a call, where the allor part of the call managers include a call manager that processes thecall and is adjacent to the call initiator;

sending, by the call initiator, a first call creating request message toan adjacent call manager according to address information of a firstcall manager in the address information of the all or part of the callmanagers; and

receiving, by the call initiator, a first call creating response messagefrom the adjacent call manager, where the first call creating responsemessage is sent by the adjacent call manager in response to the firstcall creating request message.

Correspondingly, an embodiment of the present invention further providesa call processing method, where the method includes:

obtaining, by a call manager, address information of all or part of callmanagers between the call manager and a call receiving node in a networkdomain that processes a call, where the all or part of the call managersinclude a next call manager adjacent to the call manager;

sending, by the call manager, a third call creating request message tothe next call manager according to address information of the next callmanager in the address information of the all or part of the callmanagers, where the third call creating request message includes theaddress information of the all or part of the call managers; and

receiving, by the call manager, a third call creating response messagefrom the adjacent call manager, where the third call creating responsemessage is sent by the adjacent call manager in response to the thirdcall creating request message.

Correspondingly, an embodiment of the present invention further providesa call processing method, where the method includes:

receiving a call creating request message carrying service informationand sent by a call initiating node;

obtaining address information of a call manager in a second networkdomain that processes the call according to the service information andpreconfigured topology information;

sending the call creating request message carrying the serviceinformation to the call manager of the second network domain;

receiving a call creating response message from the call manager of thesecond network domain, where, the call creating response messageincludes available link information of a call receiving node and a callidentifier (CallID) of the second network domain, and the CallID of thesecond network domain is determined on the basis of the serviceinformation;

replacing the CallID of the second network domain in the call creatingresponse message with a CallID of a first network domain, where theCallID of the first network domain is determined on the basis of theservice information, and the second network domain accesses aninformation stream of the first network domain; and

sending the replaced call creating response message to the callinitiating node.

Correspondingly, an embodiment of the present invention further providesa call processing method, where the method includes:

obtaining, by a call initiator, address information of all or part ofcall managers in a network domain that processes a call, where the allor part of the call managers include a first call manager that processesthe call and is adjacent to the call initiator;

sending, by the call initiator, a first call creating request message tothe first call manager according to address information of the firstcall manager in the address information of the all or part of the callmanagers, where the first call creating request message includes theaddress information of the all or part of the call managers;

receiving, by the first call manager, the first call creating requestmessage, deleting the address information of the first call manager inthe first call creating request message, and judging whether the callcreating request message includes address information of a second callmanager, where the second call manager is a call manager close to a callterminator and adjacent to the first call manager;

obtaining, by the first call manager, the address information of thesecond call manager, adding the address information of the second callmanager to the call creating request message, and sending the callcreating request message to the second call manager according to theobtained address information of the second call manager, when the callcreating request message does not include the address information of thesecond call manager;

sending, by the second call manager, a call creating request message toa next call manager of the second call manager, receiving a callcreating response message that is sent, according to the received callcreating request message, by the next call manager from the next callmanager of the second call manager, and sending the call creatingresponse message to the first call manager; and

sending, by the first call manager, the call creating response messageto the call initiator.

Correspondingly, a node further provided in an embodiment of the presentinvention includes:

a first address obtaining unit, adapted to obtain address information ofall or part of call managers in a network domain that processes a call,where the all or part of the call managers include a call manager thatprocesses the call and is adjacent to a call initiator;

a first request unit, adapted to send a first call creating requestmessage to an adjacent call manager according to address information ofa first call manager in the address information of the all or part ofthe call managers; and

a first response receiving unit, adapted to receive a first callcreating response message from the adjacent call manager, where thefirst call creating response message is sent by the adjacent callmanager in response to the first call creating request message.

Correspondingly, a call manager further provided in an embodiment of thepresent invention includes:

a second address obtaining unit, adapted to obtain address informationof all or part of call managers between the call manager in a networkdomain that processes a call and a call receiving node, where the all orpart of the call managers include a next call manager adjacent to thecall manager;

a second request unit, adapted to send a third call creating requestmessage to the next call manager according to address information of thenext call manager in the address information of the all or part of thecall managers, where the third call creating request message includesthe address information of the all or part of the call managers; and

a second response receiving unit, adapted to receive a third callcreating response message from the adjacent call manager, where thethird call creating response message is sent by the adjacent callmanager in response to the third call creating request message.

Correspondingly, a call manager further provided in an embodiment of thepresent invention includes: a message transceiving unit and a processingunit, where:

the message transceiving unit, adapted to receive a call creatingrequest message carrying service information and sent by a callinitiator; and

the processing unit, adapted to obtain address information of callmanagers of multiple network domains that process a call of the callinitiator, and determine a call manager that processes the callaccording to the address information.

The message transceiving unit is further adapted to forward the callcreating request message to the call manger determined by the processingunit, receive a call creating response message from the call manager,and send the call creating response message to the call initiator.

Correspondingly, a call processing system further provided in anembodiment of the present invention includes: a call initiating node, acall receiving node, and multiple call managers.

The call initiating node is adapted to send a call creating requestmessage to request for creating a call from the call initiating node tothe call receiving node.

The call manager is adapted to receive the call creating request messagecarrying service information and sent by the call initiating node,obtain address information of call managers of multiple network domainsthat process the call, determine an adjacent call manager that processesthe call according to the address information, and send the callcreating request message to the adjacent call manager; receive a callcreating response message from the adjacent call manager, and send thecall creating response message to the call initiating node; where thecall creating response message is sent by the adjacent call manageraccording to the received call creating request message.

The embodiments of the present invention have the following beneficialeffects.

In the case that a service at a client side needs to be sent throughmultiple networks at a server side, through a method, a system and adevice for call processing provided by the embodiments of the presentinvention, link selection between each network domain and admissioncontrol between each network domain are implemented through sectionprocessing performed on a call initiated by a call initiator.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a call model provided in the prior art;

FIG. 2 is a flowchart of a call processing method according to a firstembodiment of the present invention;

FIG. 3 is a flowchart of a call processing method according to a secondembodiment of the present invention;

FIG. 4 is a schematic diagram showing a first scenario of a callprocessing method according to an embodiment of the present invention;

FIG. 5 is a flowchart of a call processing method according to a thirdembodiment of the present invention;

FIG. 6 is a schematic diagram showing a second scenario of a callprocessing method according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a node according to anembodiment of the present invention;

FIG. 8 is a schematic structural diagram of a call manager according toan embodiment of the present invention; and

FIG. 9 is a schematic structural diagram of a call processing systemaccording to an embodiment of the present invention.

DETAILED DESCRIPTION

The technical solutions of embodiments of the present invention areclearly and completely described in the following with reference to theaccompanying drawings in embodiments of the present invention.Obviously, the embodiments to be described are only a part rather thanall of the embodiments of the present invention. Based on theembodiments of the present invention, all other embodiments obtained bypersons skilled in the art without creative efforts shall fall withinthe protection scope of the present invention.

FIG. 2 is a flow chart of a call processing method according to a firstembodiment of the present invention.

In the case that a service at a client side needs to be sent throughmultiple networks at a server side (it is supposed that each network atthe server side is divided into one network domain), inter-domain linkselection and admission control are implemented through section callprocessing. The call procedure includes the following steps.

S100: A call initiator obtains address information of all or part ofcall managers in a network domain that processes a call, where the allor part of the call managers include a call manager that processes thecall and is adjacent to the call initiator.

S101: The call initiator sends a first call creating request message toan adjacent call manager according to address information of theadjacent call manager in the address information of the all or part ofthe call managers.

S102: The call initiator receives a first call creating response messagefrom the adjacent call manager, where the first call creating responsemessage is sent by the adjacent call manager in response to the firstcall creating request message.

The call initiator may be a node at the client side or a node at anetwork side. In the specific implementation, the address informationincludes addresses of the all or part of the call managers in multiplenetwork domains that process the call, and the address information maybe preconfigured, or may be obtained through calculation by the callinitiator or a call manger in a first network domain according to callservice information and preconfigured topology information.

The first call creating response message includes the addressinformation of the all or part of the call managers, and the first callcreating response message is sent by the adjacent call manager after theadjacent call manager sends a second call creating request message to anext call manager of the adjacent call manager and receives a secondcall creating response message from the next call manager. The secondcall creating response message is sent by the next call manager inresponse to the second call creating request message. The second callcreating request message includes address information of the next callmanager and also includes address information of other call managers,except that of the adjacent call manager and the next call manager, inthe address information of the all or part of the call managers.

The adjacent call manager belongs to the first network domain, the nextcall manager belongs to a second network domain, and the second callcreating response message includes available inter-domain linkinformation of the first network domain and the second network domain.The first call creating response message includes available inter-domainlink information of the network domains that process the call.

Through the call processing method provided in this embodiment of thepresent invention, in the case that the service at the client side needsto be sent through multiple networks at the server side, link selectionbetween each network domain and admission control are furtherimplemented through section processing performed on the call by multiplecall managers.

FIG. 3 is a flow chart of a call processing method according to a secondembodiment of the present invention.

S200: A call manager obtains address information of all or part of callmanagers between the call manager in a network domain that processes acall and a call receiving node, where the all or part of the callmanagers include a next call manager adjacent to the call manager.

S201: The call manager sends a third call creating request message tothe next call manager according to address information of the next callmanager in the address information of the all or part of the callmanagers, where the third call creating request message includes theaddress information of the all or part of the call managers.

S202: The call manager receives a third call creating response messagefrom the next call manager, where the third call creating responsemessage is sent by the next call manager in response to the third callcreating request message.

The third call creating response message is sent by the next callmanager after the next call manager sends a fourth call creating requestmessage to an adjacent call manager of the next call manager and beingclose to a call terminator and receives a fourth call creating responsemessage from the adjacent call manager. The third call creating requestmessage includes address information of the adjacent call manager, andalso includes address information of other call managers, except that ofthe next call manager and the adjacent call manager, in the addressinformation of the all or part of the call managers.

The next call manager belongs to a third network domain, the adjacentcall manager belongs to a fourth network domain, and the fourth callcreating response message includes available inter-domain linkinformation of the third network domain and the fourth network domain.

Optionally, the call processing method of this embodiment of the presentinvention further includes: Before sending the third call creatingrequest message to the next call manager, the call manager may furtherperform admission control according to call service information andlocally configured policy information, and judges whether the callconforms to a local policy; and if yes, the call manager allows the calland executes a subsequent step of sending the third call creatingrequest message to the next call manager according to the addressinformation of the all or part of the call managers; otherwise, the callmanager refuses the call and does not execute the subsequent step.

Through the call processing method provided in this embodiment of thepresent invention, in the case that the service at the client side needsto be sent through multiple networks at the server side, link selectionbetween each network domain and admission control between each networkdomain are further implemented through section processing performed onthe call by multiple call managers.

In another embodiment of the present invention, in the case that aservice at a client side needs to be sent through multiple networks at aserver side, link selection between each network domain is implementedthrough section processing performed on a call according to a callprocessing method in this embodiment, where the method specificallyincludes:

A call initiator obtains address information of all or part of callmanagers in a network domain that processes a call, where the all orpart of the call managers include a first call manager that processesthe call and is adjacent to the call initiator.

The call initiator sends a first call creating request message to thefirst call manager according to address information of the first callmanager in the address information of the all or part of the callmanagers, where the first call creating request message includes theaddress information of the all or part of the call managers.

The first call manager receives the first call creating request message,deletes the address information of the first call manager in the firstcall creating request message, and judges whether the call creatingrequest message includes address information of a second call manager,where the second call manager is a call manager close to a callterminator and adjacent to the first call manager.

When the call creating request message does not include the addressinformation of the second call manager, the first call manager obtainsthe address information of the second call manager, adds the addressinformation of the second call manager to the call creating requestmessage, and sends the call creating request message to the second callmanager according to the obtained address information of the second callmanager.

The second call manager sends the call creating request message to anext call manager of the second call manager, receives from the nextcall manager of the second call manager a call creating response messagethat is sent, according to the received call creating request message,by the next call manager, and sends the call creating response messageto the first call manager.

The first call manager sends the call creating response message to thecall initiator.

When the call creating request message includes the address informationof the second call manager, the first call manager sends the callcreating request message to the second call manager according to theaddress information of the second call manager included in the callcreating request message.

The obtaining the address information of the second call manager by thefirst call manager includes:

The first call manager receives address information of the second callmanager designated by a network manager, or the call creating requestmessage received by the first call manager includes call serviceinformation of the call initiator and preconfigured topologyinformation.

The first call manger calculates address information of the second callmanager according to the call service information of the call initiatorand the preconfigured topology information.

The next call manager of the second call manger is a next call managerof the second call manager close to the call terminator, or the nextcall manager of the second call manger is the call terminator.

Through the call processing method provided in this embodiment of thepresent invention, in the case that the service at the client side needsto be sent through multiple networks at the server side, link selectionbetween each network domain and admission control between each networkdomain are further implemented through section processing performed onthe call by multiple call managers.

FIG. 4 is a schematic diagram showing a first scenario of a callprocessing method according to an embodiment of the present invention.

In this embodiment, take an example that a service at a client sideneeds to be sent through three networks at a server side (it is supposedthat each network at the server side is divided into one network domain)for description. Topology information is configured in each networkdomain, such as node information, intra-domain topology information,interconnection information of each network domain, and a call manageris disposed in each network domain, which is adapted to process a call.

In this embodiment of the present invention, a source node R1 and adestination node R2 are equipment at the client side, and domains 1, 2,3 and 4 jointly provide a connection service from the source node R1 tothe destination node R2, where the domains 1 and 3 access equipment atthe client side, and the domain 2 provide a sending service for thedomain 1, that is, traffic accessed by the domain 1 may be sent to thedomain 3. Specifically, the creating a call procedure from the sourcenode R1 to the destination node R2 is as follows.

(1) The source node R1 sends a call creating request message to R11 torequest for creating a call to the destination node R2, where, the callcreating request message carries service information used to indicatethe source node, the destination node and a required bandwidth of thecall.

(2) The R11 receives the call creating request message, and performsadmission control according to the service information in the callcrating request message and locally configured policy information. Thepolicy information includes maximum bandwidth information and domainroute information. In the specific implementation, local policyinformation may be configured according to actual requirements, forexample, the policy information may include: the maximum bandwidthinformation allowing access and sending from the R1 to the R2, andinformation indicating that the traffic accessed by the R1 may be sentto the R2 through the domains 2 and 3.

The R11 judges whether the call from the source node R1 to thedestination node R2 conforms to the locally configured policyinformation, for example, judges whether the bandwidth requested by thecall exceeds a locally configured maximum value, and if does not exceed,that is, the bandwidth conforms to the local policy, the R11 allows thecall, and according to the service information of the call andpreconfigured topology information, calculates to obtain addressinformation of all call managers of multiple network domains thatprocess the call, and determines a domain route from the source node R1to the destination node R2; adds the address information to the callcreating request message, and sends the call creating request message toa call manager of the next network domain that processes the call (it issupposed to be R21 of the domain 2), where the R21 and R32 aredesignated to process the call in the address information carried in thecall creating request message. If the call does not conform to thelocally configured policy, the call is refused, and the subsequentprocessing is not performed.

It should be noted that, in the specific implementation, addressinformation of call managers of each network domain may also bepreconfigured, and addresses of the call managers that processes thecall are directly obtained according to the preconfigured addressinformation during the call procedure.

(3) The R21 receives the call creating request message carrying theservice information, performs admission control according to the serviceinformation and the locally configured policy information, and judgeswhether the call conforms to the local policy, and if conforms, the callis allowed, and the call creating request message is forwarded to a callmanager of the next network domain (it is supposed to be the R32 of thedomain 3) according to the address information in the call creatingrequest message, where the R32 is designated to process the call in theaddress information carried in the call creating request message; ifdoes not conform the local policy, the call is refused.

(4) The R32 receives the call creating request message carrying theservice information, performs admission control according to the serviceinformation and the locally configured policy information, and judgeswhether the call conforms to the local policy, and if conforms, the callis allowed, and the call creating request message is forwarded to thecall manager of the next network domain (R2) according to the addressinformation in the call creating request message; if does not conformthe local policy, the call is refused.

(5) The destination node R2 accepts the call, and returns a callcreating response message to the R32. Optionally, before sending thecall creating response message to the R32, available UNI linkinformation of the R2 is added to the call creating response messageaccording to information such as a local UNI link bandwidth of the R2.

(6) The R32 receives the call creating response message returned by theR2, and forwards the call creating response message to the R21.Optionally, before sending the call creating response message to theR21, available inter-domain link information between the domain 2 andthe domain 3 is added to the call creating response message according toavailable link information between the domain 2 and the domain 3.

(7) The R21 receives the call creating response message returned by theR32, and forwards the call creating response message to the R11.Optionally, before sending the call creating response message to theR11, available inter-domain link information between the domain 1 andthe domain 2 is added to the call creating response message according toavailable link information between the domain 1 and the domain 2.

(8) The R11 receives the call creating response message returned by theR21, and forwards the call creating response message to the R1.

(9) The source node R1 receives the call creating response messagereturned by the R11, and the call is successfully created.

In a call response procedure, if the nodes R2, R32 and R21 add linkinformation in the call creating response message, the call creatingresponse message received by the R1 includes the available UNI linkinformation of the remote R2, the available inter-domain linkinformation between the domain 2 and the domain 3, and the availableinter-domain link information between the domain 1 and the domain 2.

In the preceding embodiment, the call manager R11 of the domain 1designates the addresses of the call managers of all the network domainsthat process the call from the source node R1 to the destination nodeR2. In another embodiment of the present invention, the source node R1initiating the call creating request message may also designate all (orpart) of call managers required to process a call, which is described inthe following with reference to a schematic diagram of a scenario shownin FIG. 3, and a specific processing procedure is as follows.

(1) R1 sends a call creating request message to R11 to request forcreating a call to R2, and call managers R11 and R33 required to processthe call are designated in the call creating request message, where, thecall creating request message carries service information used toindicate a source node, a destination node and a required bandwidth ofthe call.

(2) The R11 performs admission control according to traffic informationsuch as a bandwidth in the call creating request message and locallyconfigured policy information (for example, the policy informationincludes: the maximum bandwidth allowing access and sending from the R1to the R2, and traffic accessed by the R1 may be sent to the R2 throughdomains 2 and 3), judges whether the call conforms to a local policy,and if conforms, allows the call, and obtains address information ofcall managers that process the call according to the service informationand configured topology information, designates call managers R12, R21,R23, R32 and R33 required to process the call in the call creatingrequest message, and forwards the call creating request message to thenext call manager R12; if does not conform the local policy, the call isrefused.

(3) The R12 receives the call creating request message, forwards thecall creating request message to the next call manager R21, anddesignates the call managers R21, R23, R32 and R33 required to processthe call in the call creating request message.

(4) The R21 performs admission control according to the trafficinformation such as the bandwidth in the call creating request messageand the locally configured policy information (for example, the policyinformation includes: the maximum bandwidth al lowing access and sendingfrom the R12 to a domain 3), and if conforms to the local policy, thecall is passed, and the call creating request message is forwarded tothe next call manager R23, and the call managers R23, R32 and R33required to process the call is designated in the call creating requestmessage; otherwise, the call is refused.

(5) The R23 receives the call creating request message, forwards thecall creating request message to the next call manager R32, anddesignates the call managers R32 and R33 required to process the call inthe call creating request message.

(6) The R32 performs admission control according to the trafficinformation such as the bandwidth in the call creating request messageand the locally configured policy information (for example, the policyinformation includes: the maximum bandwidth allowing access and sendingform the R23 to R2), and if conforms to a local domain policy, the callis passed, and the call manager R33 required to process the call isdesignated in the call creating request message, and the call creatingrequest message is forwarded to a next call processing unit R33;otherwise, the call is refused.

(7) The R33 receives the call creating request message, and forwards thecall creating request message to a call receiver R2.

(8) The call receiver R2 accepts the call, and returns a call creatingresponse message to the R33. Optionally, before sending the callcreating response message to the R33, available UNI link information maybe added to the call creating response message according to informationsuch as a UNI link bandwidth of the R2.

(9) The R33 receives the call creating response message returned by theR2, and forwards the call creating response message to the R32.

(10) The R32 receives the call creating response message returned by theR33, and forwards the call creating response message to the R23.Optionally, before sending the call creating response message to theR23, available inter-domain link information may be added to the callcreating response message according to inter-domain link informationbetween the domain 3 and the domain 2.

(11) The R23 sends the call creating response message to the R21.

(12) The R21 receives the call creating response message returned by theR23, and forwards the call creating response message to the R12.Optionally, before sending the call creating response message to theR12, available inter-domain link information may be added to the callcreating response message according to inter-domain link informationbetween the domain 2 and domain 1.

(13) The R12 receives the call creating response message returned by theR21, and sends the call creating response message to the R11.

(14) The R11 receives the call creating response message returned by theR12, and forwards the call creating response message to the R1.

(15) The R1 receives the call creating response message returned by theR11, and the call is successfully created.

In a call response procedure, if the nodes R2, R32 and R21 add linkinformation in the call creating response message, the call creatingresponse message received by the R1 includes the available UNI linkinformation of the remote R2, the available inter-domain linkinformation between the domain 2 and the domain 3, and the availableinter-domain link information between the domain 1 and the domain 2.

In the preceding embodiment, in Step (1), the R1 may designate all callmangers required to process the call, that is, the R11, R12, R21, R23,R32 and R33 are designated to process the call in the call creatingrequest message sent to the R11.

Furthermore, after the call is successfully created, a connectioncrating procedure is started, and the source node R1 initiates aconnection creating process and sends a connection creating requestmessage to the R11. If the related available UNI link information andthe inter-domain link information are obtained through the callprocedure, a UNI link and an inter-domain link may be designated in theconnection creating request message. The connection procedure may beimplemented through General MultiProtocol Label Switching ResourceReservation Setup Protocol with Traffic-engineering Extensions (GMPLSRSVP-TE), which is well known by persons skilled in the art, and is notdescribed in detail here again.

Through the call processing method provided in this embodiment of thepresent invention, in the case that a connection from the source node tothe destination node passes through multiple networks at the serverside, section processing performed on the call by multiple networkdomains is implemented, so that link selection between each networkdomain and admission control are further implemented.

FIG. 5 is a flow chart of a call processing method according to a thirdembodiment of the present invention.

In this embodiment of the present invention, in the case that a serviceat a client side is sent through multiple networks at a server side (itis supposed that each network at the server side is divided into onenetwork domain), section processing is performed on a call by eachnetwork domain, and the method includes the following steps.

S300: A call creating request message carrying service information andsent by a source node is received.

S301: Address information of a call manager in a second network domainthat processes a call is obtained according to the service informationand preconfigured topology information.

S302: The call creating request message carrying the service informationis sent to the call manager of the second network domain.

S303: A call creating response message is received from the secondnetwork domain, where the call creating response message includesavailable link information of a destination node and a CallID of thesecond network domain.

S304: The CallID of the second network domain in the call creatingresponse message is replaced with a CallID of a first network domain,where the CallID of the first network domain is determined on the basisof the service information.

S305: The replaced call creating response message is sent to the sourcenode.

Specifically, after Step S300, the method further includes: determiningan intra-domain link of the first network domain according to theservice information and preconfigured intra-domain topology information.

After Step S301 of obtaining the address information of the call managerof the second network domain that processes the call, the method furtherincludes: determining an inter-domain link of the first network domainand the second network domain according to the service information andpreconfigured boundary link information. The call creating requestmessage is sent to the call manager of the second network domain throughthe intra-domain link of the first network domain and the inter-domainlink of the first network domain and the second network domain.

After Step S303 of receiving the call creating response message carryingthe CallID of the second network domain from the second network domain,the method further includes: recording a corresponding relation betweenthe CallID of the first network domain and the CallID of the secondnetwork domain. After Step S305 of indicating that the call issuccessfully created, the method further includes: receiving aconnection creating request message sent by the source node, where theconnection creating request message carries the service information andthe CallID of the first network domain; replacing the CallID of thefirst network domain in the connection creating request message with thecorresponding CallID of the second network domain according to thecorresponding relation between the CallID of the first network domainand the CallID of the second network domain; sending the replacedconnection creating request message to the second network domain throughthe intra-domain link of the first network domain, and the inter-domainlink of the first network domain and the second network domain; andreceiving a reservation message from the second network domain, andsending the reservation message to the source node.

Before the receiving the connection creating request message sent by thesource node, the method further includes: recording a correspondingrelation between the service information and the CallID of the firstnetwork domain. At this time, before replacing the CallID of the firstnetwork domain in the connection creating request message with thecorresponding CallID of the second network domain according to thecorresponding relation, the method further includes: judging whetherservice information corresponding to the CallID of the first networkdomain conforms to the service information carried in the connectioncreating request message, and if yes, replacing the CallID of the firstnetwork domain in the connection creating request message with thecorresponding CallID of the second network domain according to thecorresponding relation between the CallID of the first network domainand the CallID of the second network domain; otherwise, the subsequentstep is not executed.

Optionally, after the receiving the call creating request messagecarrying the service information and sent by the source node, the methodfurther includes: judging whether the service information carried in thecall creating request message conforms to a preconfigured policy, and ifyes, obtaining the address information of the call manager of the secondnetwork domain that processes the call according to the serviceinformation and the preconfigured topology information, and sending thecall creating request message carrying the service information to thecall manager of the second network domain; otherwise, the subsequentstep is not executed.

Through this embodiment of the present invention, in the case that thecall from the source node to the destination node passes throughmultiple networks at the server side, section processing performed onthe call from the source node to the destination node by multiplenetwork domains can be implemented, so that link selection between eachnetwork domain is further implemented.

FIG. 6 is a schematic diagram showing a second scenario of a callprocessing method according to an embodiment of the present invention,taking an example that a service from a source node to a destinationnode passes through three network domains for description.

In this embodiment of the present invention, domains 1, 2 and 3 jointlyprovide a connection service from a source node R1 to a destination nodeR2, where the domains 1 and 3 access equipment at a client side, and thedomain 2 provides a sending service for the domain 1, that is, trafficaccessed in the domain 1 may be sent to the domain 3. In a call creatingprocedure, a policy identifier (for example, a contract number) may becarried in a call message, and a call manager of each domain performsadmission control according to a policy corresponding to the policyidentifier. Specifically, the domains 1, 2 and 3 mutually sign acontract, and the definition is as follows.

Contract 1 (ID=1): the domain 2 is responsible for sending traffic ofthe maximum bandwidth X to the domain 3, and the domain 2 charges Y1from the domain 1.

Contract 2 (ID=2): the domain 3 may receive the traffic of the maximumbandwidth X sent by the domain 2, the traffic flows to equipment at theclient side of the domain 3, and the domain 2 charges Y2 from the domain3.

Furthermore, equipment R1 and R2 at the client side respectively accessthe domains 1 and 3, and the equipment R1 and R2 at the client sidebelong to the same client, and respectively sign a contract with thedomains 1 and 3 as follows.

Contract 3 (ID=3): the domain 1 is responsible for accessing traffic ofthe maximum bandwidth X of the equipment R1 at the client side, andcharges Y3 from the client.

Contract 4 (ID=4): the domain 3 is responsible for sending the trafficof the maximum bandwidth X to the equipment R2 at the client side, andcharges Y4 from the client.

In the specific implementation, information of the contract 3 is storedin the equipment R1 at the client side, information of the contract 4 isstored in the equipment R2 at the client side, the information of thecontract 3 and the contract 1 is stored in a node R11 of the domain 1,the information of the contract 1 and the contract 2 is stored in nodesR21 and R22 of the domain 2, and the information of the contract 2 andthe contract 4 is stored in nodes R31 and R32 of the domain 3.

Taking an example that a connection from the equipment R1 at the clientside to the equipment R2 at the client side is created through threedomains in the following, a method for implementing admission control byusing a section call processing mode is described. A call creatingprocedure is as follows.

(1) The R1 sends a call creating request message (a Notify messagedefined in a GMPLS CALL) to the R11, where the preceding message carriesservice information (the source node=R1, the destination node=R2, andthe bandwidth=X) and contract information (ID=3).

(2) The R11 receives the call creating request message, and processesthe call, which includes: examining the pre-stored contract informationand checking whether the service information carried in the callcreating request message conforms to regulations of the contractaccording to the contract number in the message; and if yes, the call isallowed, a CallID (it is supposed that CallID=10) corresponding to theservice information is distributed, and a corresponding relation betweenthe CallID and the service information is stored. The R11 determinesthat the domain 2 is used to send the service to the R2 according to theservice information, preconfigured topology information and boundarylink information, finds that a link of R12-R21 meets bandwidthrequirements, and then uses the R12 as an egress boundary node.Afterwards, the call creating request message is sent to the selectedboundary node R12, where the call creating request message carries theservice information, the CallID (CallID=10) and the contract number(ID=1).

(3) The R12 receives the call creating request message, stores theCallID (CallID=10) of the domain 1, removes the CallID from the message,and forwards the call creating request message to a boundary node R21 ofa next network domain.

(4) The R21 receives the call creating request message, examines thepre-stored contract information (the contract with ID=1 needs to be sentto the domain 3), checks whether the service information carried in thecall creating request message conforms to the regulations of thecontract, and if yes, allows the call, distributes a CallID (it issupposed that CallID=20) corresponding to the service information, andstores a corresponding relation between the CallID and the serviceinformation. The R21 determines that the domain 3 is used to send theservice to the R2 according to the service information, thepreconfigured topology information and the boundary link information,finds that a link of R23-R31 meets the bandwidth requirements, and thenuses the R23 as an egress boundary node. Afterwards, the call creatingrequest message is sent to the selected egress boundary node R23, wherethe call creating request message carries the service information, theCallID (CallID=20) and the contract number (ID=2).

(5) The R23 receives the call creating request message, stores theCallID (CallID=20) of the domain 2, removes the CallID from the message,and forwards the call creating request message to a boundary node R31 ofa next network domain.

(6) The R31 receives the call creating request message, examines thepre-stored contract information (the contract with ID=2 may receive thetraffic with the maximum bandwidth X sent by the domain 2, the trafficflows to the equipment at the client side of the domain 3) signed withthe domain 2 and the contract information (the contract with ID=4)signed with the client, checks whether the service information carriedin the call creating request message conforms to the regulations of thecontract, and if yes, allows the call, distributes a CallID (it issupposed that CallID=30) corresponding to the service information andstores a corresponding relation of the CallID and the serviceinformation. The R31 selects a route to the equipment R2 at the clientside according to the service information and the preconfigured topologyinformation, and uses the R33 as an egress boundary node. Afterwards,the call creating request message is sent to the selected egressboundary node R33, where the call creating request message carries theservice information, the CallID (CallID=30) and the contract number(ID=4).

(7) The R33 receives the call creating request message, and forwards thecall creating request message to the destination node R2.

(8) The R2 receives the call creating request message, examines thepre-stored contract information (the contract with ID=4), and checkswhether the requested service information conforms to the regulations ofthe contract; and if conforms, the call is allowed, local linkinformation is examined, an available link meeting service requirementsis selected, and a call creating response message (the Notify messagedefined in the GMPLS CALL) carrying available link information of thedestination node is constructed and sent to the R33.

(9) The R33 receives the call creating response message, and forwardsthe call creating response message to the R31.

(10) The R31 receives the call creating response message, examines linksbetween the domain 3 and the domain 2, selects an available inter-domainlink meeting the service requirements, adds the inter-domain availablelink information and the CallID (CallID=30) of the domain 3 to the callcreating response message, and forwards the call creating responsemessage to the R23.

(11) The R23 receives the call creating response message, stores theCallID (CallID=30) of the domain 3, records a corresponding relationbetween the CallID (CallID=30) and the CallID (CallID=20) of the domain2, and forwards the call creating response message to the R21.

(12) The R21 receives the call creating response message, examines linksbetween the domain 2 and the domain 1, selects an available inter-domainlink meeting the service requirements, adds the inter-domain availablelink information to the call creating response message and replaces theCallID (CallID=30) in the message with the CallID (CallID=20) of thedomain 2, and forwards the added and replaced call creating responsemessage to the R12.

(13) The R12 receives the call creating response message, stores theCallID (CallID=20) of the domain 2, records a corresponding relationbetween the CallID (CallID=20) and the CallID (CallID=10) of the domain1, and forwards the call creating response message to the R11.

(14) The R11 receives the call creating response message, replaces theCallID (CallID=20) in the call creating response message with the CallID(CallID=10) of the domain 1, and then forwards the call creatingresponse message to the R1.

(15) The R1 receives the call creating response message, where themessage includes the inter-domain available link information betweeneach network domain and the CallID (CallID=10) of the domain 1, and thecall is successfully created.

After the call is successfully created, a connection creating process isstarted, and a specific connection creating procedure is as follows.

(1) R1, according to the inter-domain available link information,determines a boundary node of each network domain that provides aconnection service, constructs a Path message (a Path message in a RSVP)carrying the service information (the source node=R1, the destinationnode=R2 and the bandwidth=X), the CallID information (CallID=10) andboundary node information (R11, R21 and R31), and sends the Path messageto the R11.

(2) The R11 receives the Path message, examines whether the serviceinformation in the message conforms to the service informationcorresponding to the CallID (CallID=10), and if conforms, calculates aroute (R11-R12-R21) to a next boundary node R21, and sends the Pathmessage to a next node R12 for requesting to create a connection.

(3) The R12 receives the Path message, where the R12 is an egressboundary node. The CallID (CallID=10) in the Path message is replacedwith the CallID (CallID=20) according to the corresponding relationbetween the CallID (CallID=10) in the Path message and the CallID(CallID=20) of the domain 2, and the Path message is sent to an ingressboundary node R21 of the domain 2.

(4) The R21 receives the Path message, examines whether the serviceinformation in the message conforms to the service informationcorresponding to the CallID (CallID=20), and if conforms, calculates aroute (R21-R23-R31) to a next boundary node R31, and sends the Pathmessage to a next node R23 for requesting to create a connection.

(5) The R23 receives the Path message, where the R23 is the egressboundary node. The CallID (CallID=20) in the Path message is replacedwith the CallID (CallID=30) according to the corresponding relationbetween the CallID (CallID=20) in the Path message and the CallID(CallID=30) of the domain 3, and the Path message is sent to an ingressboundary node R31 of the domain 3.

(6) The R31 receives the Path message, examines whether the serviceinformation in the message conforms to the service informationcorresponding to the CallID (CallID=30), and if conforms, calculates aroute (R31-R33-R2) to the destination node R2, and sends the Pathmessage to a next node R33 for requesting to create a connection.

(7) The R33 receives the Path message and directly forwards the Pathmessage to the R2.

(8) The R2 receives the Path message, constructs and sends a reservationmessage (a Resv message in the RSVP) to the R33, where the Resv messagecarries the CallID (CallID=30).

(9) The R33 receives the Resv message and forwards the Resv message tothe R31.

(10) The R31 receives the Resv message and forwards the Resv message tothe R23.

(11) The R23 receives the Resv message, replaces the CallID (CallID=30)in the Resv message with the CallID (CallID=20) according to thecorresponding relation between the CallID (CallID=30) in the Resvmessage and the CallID (CallID=20) of the domain 2, and sends the Resvmessage to the R21.

(12) The R21 receives the Resv message and forwards the Resv message toa previous node R12.

(13) The R12 receives the Resv message, replaces the CallID (CallID=20)in the Resv message with the CallID (CallID=10) according to thecorresponding relation between the CallID (CallID=20) in the Resvmessage and the CallID (CallID=10) of the domain 1, and sends the Resvmessage to the R11.

(14) The R11 receives the Resv message and forwards the Resv message tothe R1.

(15) The R1 receives the Resv message, and the connection issuccessfully created.

In the specific implementation, in the steps (2), (4) and (6) of thecall creating procedure, an intra-domain link of a network domain, andan inter-domain link of the network domain and a downstream adjacentnetwork domain may be respectively calculated (if the calculation of theintra-domain link fails, the call is refused), a mapping relationbetween the CallID of the network domain and the intra-domain link, anda mapping relation between the CallID of the network domain and theinter-domain link of the network domain and the downstream adjacentnetwork domain are created and stored. Therefore, in the steps (2), (4)and (6) of the connection creating procedure, the correspondingintra-domain link and inter-domain link may be examined according to theCallID, and re-calculation of the intra-domain link and the inter-domainlink is not required, thus ensuring that the intra-domain link and theinter-domain link both have resources and that the service issuccessfully created.

Through the call processing method provided in this embodiment of thepresent invention, in the case that the service from the source node tothe destination node passes through multiple networks at a server side,section processing performed on the call from the source node to thedestination node by multiple network domains can be implemented, so thatlink selection between each network domain and admission control betweeneach network domain are further implemented.

In the preceding, the connection from the source node to the destinationnode passing through three network domains is merely an example fordescription, but the implementation of the present invention is notlimited to this, and may also be applicable to a scenario where multiplenetwork domains exist between a source node and a destination node.

The definition of the call message in the GMPLS Call in the prior art isas follows:

  <Notify message> ::= <Common Header> [ <INTEGRITY> ]        [[<MESSAGE_ID_ACK> |        <MESSAGE_ID_NACK>]...]        [ <MESSAGE_ID> ]      <ERROR_SPEC>       <notify session list>   <notify sessionlist> ::= [ <notify session list> ] <notify session>   <notifysession> ::= <SESSION> [ <ADMIN_STATUS> ]         [ <POLICY_DATA>...]        [ <LINK_CAPABILITY> ]         [ <SESSION_ATTRIBUTE> ]        [ <sender descriptor> | <flow descriptor> ]   <senderdescriptor> ::= <SENDER_TEMPLATE>   <SENDER_TSPEC>   <flowdescriptor> ::= see [RFC3473]

The objects such as <LINK_CAPABILITY> and <POLICY_DATA> in the prior artcannot be processed in sections, and the <LINK_CAPABILITY> object islink information of a call destination node by default, and therefore, adesignated node of the link information is not displayed in a responsemessage. If inter-domain link information needs to be carried, adesignated node of an inter-domain link and a designated node of a UNIlink need to be displayed in a message.

In order to eliminate a defect that call section processing is notsupported in the prior art, a first embodiment of the call processingmethod provided in this embodiment of the present invention and appliedin a GMPLS Call message is as follows:

  <Notify message> ::= <Common Header> [ <INTEGRITY> ]       [[    <MESSAGE_ID_ACK>    | <MESSAGE_ID_NACK>]...]       [ <MESSAGE_ID> ]       <ERROR_SPEC>       <notify session list>  <notify session list> ::= [ <notify session list> ] <notify session>  <notify session> ::= <SESSION> [ <ADMIN_STATUS> ]       [ <SESSION_ATTRIBUTE> ]        [ <sender descriptor> | <flowdescriptor> ]        [ <call manager list> ]   < call manager list > ::=[ < call manager list > ] < call manager >   <callmanager>::=<callmanageraddress>[<POLICY_DATA>...]        [<node id><LINK_CAPABILITY> ]   <sender descriptor> ::= see [RFC3473]   <flowdescriptor> ::= see [RFC3473]

As for a format of a call creating request message and a call creatingresponse message, reference may be made to the preceding embodiment,where, the <call manager list> object is added to implement functions ofinter-domain link selection and admission control through sectionprocessing, that is, call content required to be processed by each callmanager is designated, and addresses of the call managers are designatedin <call manager address>. In the specific implementation, the objectssuch as <POLICY_DATA> may be designated to carry the content required tobe processed according to the requirements, and the related contentsrequired to be processed by other call managers may be designated in the<notify session> object.

In a response message, a <node id> object is added before<LINK_CAPABILITY>, which is used to indicate the node ID of the linkinformation.

An executable solution of a call protocol extension method is describedin the preceding, and other call protocol extension methods may also beadopted in this embodiment of the present invention. A second embodimentof the call processing method provided in this embodiment of the presentinvention and applied in the GMPLS Call message is as follows:

  <Notify message> ::= <Common Header> [ <INTEGRITY> ]       [[    <MESSAGE_ID_ACK>    | <MESSAGE_ID_NACK>]...]        [<MESSAGE_ID> ]       <ERROR_SPEC>   <notify session list>   <notifysession list> ::= [ <notify session list> ] <notify session>   <notifysession> ::= <SESSION> [ <ADMIN_STATUS> ]        [<POLICY_DATA>...] [<LINK_CAPABILITY> ] [ <SESSION_ATTRIBUTE> ]       [<Call_ERO> ]   [<sender descriptor> | <flow descriptor> ]   <sender descriptor> ::= see[RFC3473]   <flow descriptor> ::= see [RFC3473]

In this embodiment, <Call_ERO> carries addresses of each call manager.<POLICY_DATA> is a unified policy of each network domain (for example,responsible for the sending of a service at the same client side), andthe policy information is not required to be separately carried afterthe addresses of each call manager.

A third embodiment of the call processing method provided in thisembodiment of the present invention and applied in the GMPLS Callmessage is as follows:

  <Notify message> ::= <Common Header> [ <INTEGRITY> ]        [[<MESSAGE_ID_ACK> |        <MESSAGE_ID_NACK>]...]        [  <MESSAGE_ID>]       <ERROR_SPEC>       <notify session list>   <notify session list>::= [ <notify session list> ] <notify session>   <notify session> ::=<SESSION> [ <ADMIN_STATUS> ]      [ <SESSION_ATTRIBUTE> ]      [ <senderdescriptor> | <flow descriptor> ]      [ <call manager list> ]   < callmanager list > ::= [ < call manager list > ] < call manager >  <callmanager> ::=<callmanageraddress>[<POLICY_DATA>...]      [<nodeid> <LINK_CAPABILITY> ]   <sender descriptor> ::= see [RFC3473]   <flowdescriptor> ::= see [RFC3473]

The added <call manager list> object is used to implement the functionsof the inter-domain link and the admission control through the sectionprocessing, and the content of the object is a reachable address of acall manager. A <node id> object is added before <LINK_CAPABILITY>,which is used to indicate a node of the link.

FIG. 7 is a schematic structural diagram of a node according to anembodiment of the present invention, and the node includes a firstaddress obtaining unit 701, a first request unit 702, and a firstresponse receiving unit 703.

The first address obtaining unit 701 is adapted to obtain addressinformation of all or part of call managers in a network domain thatprocesses a call, where the all or part of the call managers include acall manager that processes the call and is adjacent to a callinitiator.

The first request unit 702 is adapted to send a first call creatingrequest message to an adjacent call manager according to addressinformation of the adjacent call manager in the address information ofthe all or part of the call managers.

The first response receiving unit 703 is adapted to receive a first callcreating response message from the adjacent call manager, where thefirst call creating response message is sent by the adjacent callmanager in response to the first call creating request message.

FIG. 8 is a schematic structural diagram of a call manager according toan embodiment of the present invention, and the call manager includes asecond address obtaining unit 801, a second request unit 802, and asecond response receiving unit 803.

The second address obtaining unit 801 is adapted to obtain addressinformation of all or part of call managers between the call manager ina network domain that processes a call and a call receiving node, wherethe all or part of the call managers include a next call manageradjacent to the call manager.

The second request unit 802 is adapted to send a third call creatingrequest message to the next call manager according to addressinformation of the next call manager in the address information of theall or part of the call managers, where the third call creating requestmessage includes the address information of the all or part of the callmanagers.

The second response receiving unit 803 is adapted to receive a thirdcall creating response message from the next call manager, where thethird call creating response message is sent by the next call manager inresponse to the third call creating request message.

FIG. 9 is a schematic structural diagram of a call processing systemaccording to an embodiment of the present invention, and the systemincludes a source node 901, a destination node 902, and multiple callmanagers 903.

The source node 901 is adapted to send a call creating request messagecarrying service information to request for creating a call from thesource node 901 to the destination node 903.

One of the call managers 903 is adapted to receive the call creatingrequest message carrying the service information and sent by the sourcenode 901, obtain address information of call managers of multiplenetwork domains that process the call from the source node 901 to thedestination node 903, determine a call manager that processes the callaccording to the address information, forward the call creating requestmessage to the call manager, receive a call creating response messagefrom the call manager, and send the call creating response message tothe source node 901.

Specifically, the call manager 903 includes: a message transceiving unit9031 and a processing unit 9032.

The message transceiving unit 9031 is adapted to receive the callcreating request message carrying the service information and sent bythe source node 901.

The processing unit 9032 is adapted to obtain the address information ofthe call managers of multiple network domains that process the call fromthe source node 901 to the destination node 903, and determine the callmanager that processes the call according to the address information.

The message transceiving unit 9031 is further adapted to forward thecall creating request message to the call manger determined by theprocessing unit 9032, receive a call creating response message from thecall manager, and send the call creating response message to the sourcenode 901.

In an embodiment of the call manager provided in the present invention,the processing unit of the call manager specifically includes: aninter-domain link determining module, an admission control module, anintra-domain link determining module, a CallID configuration module, anda replacing module.

The inter-domain link determining module is adapted to determineavailable inter-domain link information between a first network domainand a second network domain, and add the available inter-domain linkinformation to a call creating response message.

The admission control module is adapted to judge whether the callconforms to a local policy according to call service information of acall initiator and locally configured policy information, and if yes,the call is allowed.

The intra-domain link determining module is adapted to determineintra-domain link of the first network domain according to the serviceinformation in the call creating request message and preconfiguredintra-domain topology information.

The CallID configuration module is adapted to configure a CallID of thefirst network domain according to the service information carried in thecall creating request message.

The replacing module is adapted to replace a CallID of the secondnetwork domain with the CallID of the first network domain in the callcreating response message.

Through a method, a system and a device for call processing provided inthe embodiments of the present invention, in the case that a service ata client side needs to be sent through multiple networks at a serverside, link selection between each network domain and admission controlbetween each network domain are implemented through section callprocessing.

Those of ordinary skill in the art may understand that all or part ofthe steps of the method according to the embodiments may be implementedby a program instructing relevant hardware. The program may be stored ina computer readable storage medium. When the program is run, the stepsof the method according to the embodiments are performed. The storagemedium may be a magnetic disk, an optical disk, a Read-Only Memory(ROM), and a Random Access Memory (RAM).

The preceding descriptions are exemplary embodiments of the presentinvention, and it should be noted that, any modification or improvementmade without departing from the principle of the present invention bythose of ordinary skill in the art should also fall within theprotection scope of the present invention.

What is claimed is:
 1. A call processing method, comprising: obtaining,by a call initiator, address information of all or part of call managersin network domains that process a call, wherein the all or part of thecall managers comprise a call manager that processes the call and isadjacent to the call initiator; sending, by the call initiator, a firstcall creating request message to an adjacent call manager according toaddress information of the adjacent call manager in the addressinformation of the all or part of the call managers, the first callcreating request message carries service information, performing, by theadjacent call manager, admission control according to the serviceinformation in the first call creating request message and locallyconfigured policy information; and receiving, by the call initiator, afirst call creating response message from the adjacent call manager,wherein the first call creating response message is sent by the adjacentcall manager in response to the first call creating request message. 2.The call processing method according to claim 1, wherein the first callcreating request message comprises the address information of the all orpart of the call managers, the first call creating response message issent by the adjacent call manager after the adjacent call manager sendsa second call creating request message to a next call manager of theadjacent call manager and receives a second call creating responsemessage from the next call manager; and the second call creatingresponse message is sent by the next call manager in response to thesecond call creating request message; and the second call creatingrequest message comprises address information of the next call manager,and further comprises address information of other call managers, exceptthat of the adjacent call manager and the next call manager, in theaddress information of the all or the part of the call managers.
 3. Thecall processing method according to claim 2, wherein the adjacent callmanager belongs to a first network domain, the next call manager belongsto a second network domain, and the second response message comprisesavailable inter-domain link information between the first network domainand the second network domain.
 4. The call processing method accordingto claim 1, wherein the first call creating response message comprisesavailable inter-domain link information between the network domains thatprocess the call.
 5. The call processing method according to claim 1,wherein the address information of the all or part of the call managersis preconfigured, or the address information of the all or part of thecall managers is obtained through calculation by the call initiatoraccording to call service information of the call initiator andpreconfigured topology information.
 6. A call processing method,comprising: obtaining, by a call manager, address information of all orpart of call managers between the call manager in a network domain thatprocesses the call and a call receiving node, wherein the all or part ofthe call managers comprise a next call manager adjacent to the callmanager; sending, by the call manager, a third call creating requestmessage to the next call manager according to address information of thenext call manager in the address information of the all or part of thecall managers, wherein the third call creating request message comprisesthe address information of the all or part of the call managers; andreceiving, by the call manager, a third call creating response messagefrom the next call manager, wherein the third call creating responsemessage is sent by the next call manager in response to the third callcreating request message; wherein before the sending, by the callmanager, the third call creating request message to the next callmanager, the method further comprises: performing, by the call manager,admission control according to call service information and locallyconfigured policy information.
 7. The call processing method accordingto 6, wherein the third call creating response message is sent by thenext call manager after the next call manager sends a fourth callcreating request message to an adjacent call manager of the next callmanager and being close to a call terminator and receives a fourth callcreating response message from the adjacent call manager; and the thirdcall creating request message comprises address information of theadjacent call manager, and further comprises address information ofother call managers, except that of the next call manager and theadjacent call manager, in the address information of the all or part ofthe call managers.
 8. The call processing method according to claim 7,wherein the next call manager belongs to a third network domain, theadjacent call manager belongs to a fourth network domain, and the fourthcall creating response message comprises available inter-domain linkinfo Ration between the third network domain and the fourth networkdomain.
 9. A call processing method, comprising: receiving a callcreating request message carrying service information and sent by a callinitiating node; obtaining address information of a call manager in asecond network domain that processes the call according to the serviceinformation and preconfigured topology information; sending the callcreating request message carrying the service information to the callmanager of the second network domain; receiving a call creating responsemessage from the call manager of the second network domain, wherein thecall creating response message comprises available link information of acall receiving node and a call identifier (CallID) of the second networkdomain, and the CallID of the second network domain is determined on thebasis of the service information; replacing the CallID of the secondnetwork domain in the call creating response message with a CallID of afirst network domain, wherein the CallID of the first network domain isdetermined on the basis of the service information, and the secondnetwork domain accesses an information stream of the first networkdomain; and sending the replaced call creating response message to thecall initiating node.
 10. The call processing method according to claim9, wherein after the receiving the call creating response message fromthe call manager of the second network domain, the method furthercomprises: recording a corresponding relation between the CallID of thefirst network domain and the CallID of the second network domain; andafter sending the replaced call creating response message to a callinitiator, the method further comprises: receiving a connection creatingrequest message sent by the call initiator, wherein the connectioncreating request message carries the service information and the CallIDof the first network domain; replacing the CallID of the first networkdomain in the connection creating request message with the CallID of thesecond network domain according to the corresponding relation betweenthe CallID of the first network domain and the CallID of the secondnetwork domain, and sending the replaced connection creating requestmessage to the second network domain; and receiving a reservationmessage from the second network domain, and sending the reservationmessage to the call initiator.
 11. The call processing method accordingto claim 10, wherein before the receiving the connection creatingrequest message sent by the call initiator, the method furthercomprises: recording a corresponding relation between the serviceinformation and the CallID of the first network domain; and afterreceiving the connection creating request message sent by the callinitiating node, the method further comprises: determining whetherservice information corresponding to the CallID of the first networkdomain in the connection creating request message conforms to theservice information carried in the connection creating request message;if yes, replacing the CallID of the first network domain in theconnection creating request message with the CallID of the secondnetwork domain according to the corresponding relation between theCallID of the first network domain and the CallID of the second networkdomain; and sending the replaced connection creating request message tothe second network domain.
 12. A call processing system, comprising acall initiating node, a call receiving node, and multiple call managers,wherein the call initiating node is adapted to send a call creatingrequest message to request for creating a call from the call initiatingnode to the call receiving node; and one of the call managers is adaptedto receive the call creating request message carrying serviceinformation and sent by the call initiating node, perform admissioncontrol according to the service information and locally configuredpolicy information, obtain address information of call managers ofmultiple network domains that process the call, determine an adjacentcall manager that processes the call according to the addressinformation, send the call creating request message to the adjacent callmanager, receive a call creating response message from the adjacent callmanager, and send the call creating response message to the callinitiating node, wherein the call creating response message is sent bythe adjacent call manager according to the received call creatingrequest message.